Metadata Object Description Schema

Metadata Object Description Schema (MODS)

MODS Logo

The Metadata Object Description Schema (MODS) is an XML-based bibliographic description schema developed by the United States Library of Congress' Network Development and Standards Office. MODS was designed as a compromise between the complexity of the MARC format used by libraries and the extreme simplicity of Dublin Core metadata.

Contents

About MODS

History and development

MODS was first announced for trial use in June, 2002. As of June 2010 it is at version 3.4[1].

The number of users of MODS is unknown. Implementers are encouraged to register their uses of MODS in the implementation registry on the official MODS website. To date there are about 35 projects listed in the registry, although it is assumed that many others are making use of the standard. Users are primarily operating in the area of digital libraries, and some of the registered uses are in digital library projects at the Library of Congress.

Relationship to MARC

The MODS record has been designed to carry key data elements from the MARC record but does not define all of the MARC fields and does not use the field and subfield tagging from the MARC standard. There are data elements in MODS that are not compatible with the MARC record so there is some loss translating from MARC to MODS and from MODS to MARC. There is no commitment on the part of the Library of Congress to maintain compatibility between the two metadata formats beyond what is convenient to the community of MODS users

MARC Mapping to MODS

                 Mapping for MARC 21 bibliographic records

MARC Tag MODS Elements

titleInfo <titleInfo>

[If $f$g$k follow $b they go with <subTitle>. If they follow $a they go with <title>.]

                                                        add attribute lang="content of subfield"

8246 $i displayLabel="text of $i"

880$6=245, 210,246,130,240,730,740 (with subfields as above) Repeat <titleInfo>, transform field as above with altRepGrp=""[1 digit character incrementing each pair]; Add also matching altRepGrp to equivalent element. name (use only if no $t)

use text "creator" if desired, to maintain indication of "main entry"

110 with 240	add nameTitleGroup="1"

use text "creator" if desired, to maintain indication of "main entry"

880$6=100,700,110,710,111,711,720 (with subfields as above)	Repeat <name>, transform field as above with altRepGrp=""[1 digit character  incrementing each pair]; Add also matching altRepGrp to equivalent element

typeOfResource Leader/06 <typeOfResource> with

  	if Leader/07 (code c)	    	 attribute collection="yes"
  	if Leader/06 (codes d,f,p,t)	   	 attribute manuscript="yes"
	   	   	and value:
 	 a, t	   	 text
 	 e, f	   	 cartographic
 	 c, d	   	 notated music
 	 i, j	   	 sound recording

[Used when a sound recording contains a mixture of musical and nonmusical sound or if the user does not need to make a distinction between musical and nonmusical sound recordings]

	i	 	sound recording - nonmusical
	j	 	sound recording - musical
 	 k	   	 still image

[not exact mapping; some still images coded "g"]

 	 g	   	 moving image
	o	 	kit
 	 r	   	 three dimensional object
 	 m	   	 software, multimedia
 	 p	   	 mixed material

genre <genre> various positions <genre authority="marcgt"> [repeat tag for each new value] and value [where two MARC elements are indicated, only generate one <genre>]:

  	or 007/01 MP (code d)	   

 	or 008/26 CF (code e)	   

 	or 007/01 MP (code j)	   

	or 007/01 MP (code q)

<genre> with

 	 655 $2	   	 attribute authority="contents of $2"

[Generate "-" between each subfield from MARC on output in MODS.] 655 $0 add xlink="contents of $0" (as URI) 880$6=047,655 (with subfields as above) Repeat <genre>, transform field as above with altRepGrp=""[1 digit character incrementing each pair]; Add also matching altRepGrp to equivalent element originInfo <originInfo>

dition> Leader/07 <issuance>

 	if Leader/07 (code b)	   	then value: continuing
 	if Leader/07 (code a,c,d)	   	then value: monographic
	if Leader/07 (code m) and Leader/19 (code a,b, or c)	 	then value: multipart monograph
	if Leader/07 (code m) and Leader/19 (code #)	 	then value: single unit
	if Leader/07 (code i)	 	then value: integrating resource
	if Leader/07 (code s)	 	then value: serial
	 

subfields as above)	Repeat <language>, transform field as above with altRepGrp=""[1 digit character incrementing each pair]; Add also matching altRepGrp to equivalent element

physicalDescription <physicalDescription>

hority="marcsmd"> and value: Electronic Resource

	(code b)	 	chip cartridge
	(code c)	 	computer optical disc cartridge
	(code j)	 	magnetic disc
	(code m)	 	magneto-optical disc
	(code o)	 	optical disc
	(code r)	 	remote
	(code a)	 	tape cartridge
	(code f)	 	tape cassette
	(code h)	 	tape reel

Globe (code a) celestial globe

	(code e)	 	earth moon globe
	(code b)	 	planetary or lunar globe
	(code c)	 	terrestrial globe

Kit

	(code o)	 	kit

Map

	(code d)	 	atlas
	(code g)	 	diagram
	(code j)	 	map
	(code q)	 	model
	(code k)	 	profile
	(code r)	 	remote-sensing image
	(code s)	 	section
	(code y)	 	view

Microform

	(code a)	 	aperture card
	(code e)	 	microfiche
	(code f)	 	microfiche cassette
	(code b)	 	microfilm cartridge
	(code c)	 	microfilm cassette
	(code d)	 	microfilm reel
	(code g)	 	microopaque

Motion Picture

	(code c)	 	film cartridge
	(code f)	 	film cassette
	(code r)	 	film reel

Nonprojected Graphic

	(code n)	 	chart
	(code c)	 	collage
	(code d)	 	drawing
	(code o)	 	flash card
	(code e)	 	painting
	(code f)	 	photomechanical print
	(code g)	 	photonegative
	(code h)	 	photoprint
	(code i)	 	picture
	(code j)	 	print
	(code l)	 	technical drawing

Notated Music

	(code q)	 	notated music

Projected Graphic

	(code d)	 	filmslip
	(code c)	 	filmstrip cartridge
	(code o)	 	filmstrip roll
	(code f)	 	other filmstrip type
	(code s)	 	slide
	(code t)	 	transparency

Remote-sensing Image

	(code r)	 	remote-sensing image

Sound Recording

	(code e)	 	cylinder
	(code q)	 	roll
	(code g)	 	sound cartridge
	(code s)	 	sound cassette
	(code d)	 	sound disc
	(code t)	 	sound-tape reel
	(code i)	 	sound-track film
	(code w)	 	wire recording

Tactile Material

	(code c)	 	braille
	(code b)	 	combination
	(code a)	 	moon
	(code d)	 	tactile, with no writing system

Text

	(code c)	 	braille
	(code b)	 	large print
	(code a)	 	regular print
	(code d)	 	text in looseleaf binder

Videorecording

	(code c)	 	videocartridge
	(code f)	 	videocassette
	(code d)	 	videodisc
	(code r)	 	videoreel

008/23 MU,MM or 008/29 MP, VM <form authority="marcform"> and value:

	(code f)	 	braille
	(code s)	 	electronic
	(code b)	 	microfiche
	(code a)	 	microfilm
	(code blank, r)	 	print

(code blank, r) print

Leader/06 (code m) <form authority="marcform">electronic

130,240,242,245,246,730$h, 256,300,856 (with subfields as above) Repeat <physicalDescription>, transform field as above with altRepGrp=""[1 digit character incrementing each pair]; Add also matching altRepGrp to equivalent element abstract

=520 Repeat <abstract>, transform field as above with altRepGrp=""[1 digit character incrementing each pair]; Add also matching altRepGrp to equivalent element tableOfContents

=505 (with subfields as above) Repeat <tableOfContents>, transform field as above with altRepGrp=""[1 digit character incrementing each pair]; Add also matching altRepGrp to equivalent element targetAudience <targetAudience> 521 $a$b <targetAudience>

ind 1=4 add attribute displayLabel="Motivation or interest level "

various positions <targetAudience authority="marctarget"> 008/22 BK,CF,MU,VM and value:

 	 (code d)	   	 adolescent
	 (code e)	   	 adult
 	 (code g)	   	 general
 	 (code b,c,j)	   	 juvenile
 	 (code a)	   	 preschool
 	 (code f)	   	 specialized

880$6=521 (with subfields as above) Repeat <targetAudience>, transform field as above with altRepGrp=""[1 digit character incrementing each pair]; Add also matching altRepGrp to equivalent element note

$c,362$a$z,5XX (all fields in 500-599 range with subfields as above if listed) Repeat <note>, transform field as above with altRepGrp=""[1 digit character incrementing each pair]; Add also matching altRepGrp to equivalent element subject <subject> 600, 610, 611, 630,648, 650, 651 <subject authority> with attribute:

	ind2=0	                                <subject authority="lcsh">
	ind2=1	                                <subject authority="lcshac">
	ind2=2	                                <subject authority="mesh">
	ind2=5	                                <subject authority="csh">
	ind2=3	                                <subject authority="nal">
	ind2=6	                                <subject authority="rvm">
	ind2=7	                                <subject authority="contents of $2">

(with subfields as above) Repeat <subject>, transform field as above with altRepGrp=""[1 digit character incrementing each pair]; Add also matching altRepGrp to equivalent element classification <classification>

relatedItem <relatedItem> MARC related item data fields:

	All 760-787

All 800-830

nd2=2 type attributes for all related item data:

, 710, 711, 730, 740 ind2=2 and 770, 774 type="constituent"

ind2=2	[no type specified]

displayLabel attribute for all related item data: 760, 762, 765, 767, 770, 772, 773, 774, 775,776, 777, 780, 785, 786, 787 $i add attribute displayLabel="contents of subfield $i" 773 $3 add attribute displayLabel="contents of subfield $3"

title subelement:

$a$v	 <title> and

$n (after $t for 710, 810, 711, 811) in all fields above <partNumber>

$p in fields 773 and 786 <partName>

$v <partNumber>

<partNumber>

760, 762, 765, 767, 770, 772, 773, 774, 775,776, 777, 780, 785, 786, 787 $s <title> with <titleInfo> type="uniform" and 760, 762, 765, 767, 770, 772, 774, 775,776, 777, 780, 785, 786, 787 $g <partNumber>

name subelement:

Bulleted list item
Bulleted list item

700, 800

   $a$q ($g before $t)	<name> with type="personal"
   $b$c	<namePart> with type="termsOfAddress"
   $d	<namePart> with type="date"
   $e	<role><roleTerm> with type="text"
   $4	<role><roleTerm> with type="code"

710, 810

   $a
   $b
   $c ($d$g$n before $t)
   $e
   $4	 <name> with type="corporate"

<namePart> <namePart> <namePart> <role><roleTerm> with type="text" <role><roleTerm> with type="code" 711,811

   $a$q$d$c ($g$n before $t)
   $4	 <name> with type="conference"

<namePart> add <role><roleTerm> with type="code"

, 775, 776, 777, 780, 785, 786, 787 $a <name> with no type attribute

originInfo subelement: <originInfo> 775$f <place><placeTerm> with type="code"

language subelement: 775$e <language><languageTerm> with type="code" and authority="iso639-2b"

physical description subelement: <physicalDescription>

Advantages

The use of MODS provides several advantages compared to other metadata schemas[2]: 

High compatibility with existing resource descriptions
Less detail than MARC so various internal record element sets can be mapped to MODS
Item descriptions from outside in DC and other simpler formats can be mapped and enhanced

Maintenance board

Revisions to the schema are suggested and discussed on the MODS listserv, and approved by the MODS Editorial Committee. The MODS/MADS Editorial Committee is an international group of volunteers responsible for maintaining editorial control over MODS and MADS and their accompanying documentation as well as for the MODS and MADS XML schemas[3]. The Library of Congress carries out the application of approved changes to the schema and maintains the official web site for the standard.  There is no formal standards body involved in the MODS schema at this time. 
==See also==

Comparison of reference management software for software supporting the MODS format.
Metadata Authority Description Schema was created to serve as a companion to the Metadata Object Description Schema (MODS).[1]
Metadata standards

References

  1. ^ "MODS and MADS: Current implementations and future directions". http://presentations.ala.org/images/1/1f/Riley.pdf. Retrieved 2011-08-01. 
  2. ^ "Using MODS for discovery of LC’s rich collections". http://presentations.ala.org/images/e/e3/Mccallum_guenther.pdf. Retrieved 2011-08-02. 
  3. ^ "MODS/MADS Editorial Committee". http://www.loc.gov/standards/mods/editorial-committee.html. Retrieved 2011-08-02. 
4

http://www.loc.gov/standards/mods/mods-mapping.html

External links

Official website
MODS listserv Site